Execution using multiple page tables

ABSTRACT

Embodiments of techniques and systems for execution of code with multiple page tables are described. In embodiments, a heterogenous system utilizing multiple processors may use multiple page tables to selectively execute appropriate ones of different versions of executable code. The system may be configured to support use of function pointers to virtual memory addresses. In embodiments, a virtual memory address may be mapped, such as during a code fetch. In embodiments, when a processor seeks to perform a code fetch using the function pointer, a page table associated with the processor may be used to translate the virtual memory address to a physical memory address where code executable by the processor may be found. Usage of multiple page tables may allow the system to support function pointers while utilizing only one virtual memory address for each function that is pointed to. Other embodiments may be described and claimed.

BACKGROUND

Heterogenous computing systems and devices (e.g., systems that usemultiple distinct computing processors based on different instructionset architectures) are used in many computing scenarios. For example, insome devices, a separate CPU and CPU may be situated on the same die. Invarious systems, the computing processors may be configured to executeinstructions based on non-identical instruction set architectures(ISAs). The use of heterogenous processors can provide processing,space, and resources efficiencies. For example, two processors that lieon the same die may each have access to a common memory; this sharedmemory allows the same data to be easy accessed by both processors.

However, resource sharing can also lead to problems in some heterogenouscomputing systems. One such problem comes when using program languagesthat support the use of function pointers, which allow a pointer to afunction to be passed as data between threads. These function pointersare not frequently well supported (or supported at all) in traditionalsystems with heterogenous processors using different ISAs. For example,if a pointer is created to a function that is written in a first ISA fora first processor, that same pointer could end up being passed to athread running on a second processor. If the second processor attemptsto execute the function pointed to by the function pointer, there willusually be an error because the second processor will attempt to executea function written in an unsupported ISA. Some systems attempt to dealwith this by storing two pointers for each function, but this does notwork well in all languages, such as, for example, C and C++.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example, and not by wayof limitation, in the figures of the accompanying drawings.

FIG. 1 illustrates an example heterogenous execution system withmultiple page tables, in accordance with various embodiments.

FIG. 2 illustrates an example virtual machine monitor of theheterogenous execution system with multiple page tables, in accordancewith various embodiments,

FIG. 3 illustrates an example heterogenous execution system withmultiple page tables execution process, in accordance with variousembodiments.

FIG. 4 illustrates an example heterogenous execution s system withmultiple page tables loading process, in accordance with variousembodiments.

FIG. 5 illustrates an example heterogenous execution system withmultiple page tables code fetch process, in accordance with variousembodiments.

FIG. 6 illustrates an example computing environment suitable forpracticing the disclosure, in accordance with various embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay he made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents,

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrase “A and/or B”means (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

As used herein, the term “module” may refer to, be part of or include anApplication Specific Integrated Circuit (“ASIC”), an electronic circuit,a processor (shared, dedicated, or group) and/or memory (shared,dedicated, or group) that execute one or more software or firmwareprograms, a combinational logic circuit, and/or other suitablecomponents that provide the described functionality.

Referring to FIG. 1, a block diagram is shown illustrating aheterogenous execution system with multiple page tables 100 (“HES 100”).In various embodiments, the HES 100 may be configured to selectivelyexecute appropriate ones of different versions of executable code in theheterogenous processor environment. In various embodiments, the HES 100may be configured to support use of function pointers to virtual memoryaddresses for executable code through the use of multiple page tables.Thus, in embodiments of the HES 100, a function pointer may include avirtual memory address that is mapped, such as by a one of the multiplepage tables, to a physical memory address that contains executable codethat is executable by the processor utilizing the function pointer. Themapping may be used during virtual memory address translations, such asduring a code fetch. In embodiments, when another processor of the 100seeks to perform its own code fetch using the function pointer, a secondpage table associated with the other processor may be used to translatethe virtual memory address to a different physical memory address wherecode executable by the other processor may be found. This usage ofmultiple page tables allows the HES 100 to support function pointerswhile utilizing only one virtual memory address for each function thatis pointed to.

As illustrated, in embodiments, a portion of source code 105 (e.g., afunction) may be compiled by a compiler 110 into multiple versions ofexecutable code (such as illustrated versions of executable code 113 and115). In various embodiments, the compiler 110 may be configured withknowledge of the HES 100, and in particular of one or more processorsthat are used in the HES 100. In embodiments, when the compiler 110 isso configured, the compiler 110 may generate the versions of executablecode 113 and 115 to use instructions from the various ISAs of theprocessors used in the HES 100. For example, as illustrated in FIG. 1,in various embodiments the compiler 110 may compile a portion of thesource code 105 into executable code for a CPU (113) as well asexecutable code for a GPU (115). In various embodiments, the source code105 may comprise main line code and one or more functions; one or moreof these functions may be compiled into the versions of executable code113 and 115. In alternate embodiments, the different versions of theexecutable code may be compiled using different compilers, such as bysoftware developers, with the compilers targeted for processors ofdifferent ISA.

The different versions of the executable code 113 and 115 may then beloaded by a loader 120, which may, in various embodiments, optionally beincluded in the HES 100 or may be a separate component or module. Invarious embodiments, the loader 120 may be configured to load thedifferent versions of executable code 113 and 115 into physical memory160. For example, as illustrated, the different versions of executablecode 113 and 115 may be stored in physical memory at separate sets ofphysical memory addresses, such as the illustrated sets EC 1 physicaladdresses 170 and EC 2 physical addresses 180. In various embodiments,the loader 120 may also be configured to configure or to facilitateconfiguration of page tables (such as illustrated page tables 140 and150) to support various virtual memory address translation activitiesdescribed herein. Particular examples of activities performed by theloader 120 are described below.

In embodiments, the HES 100 may be configured with one or moreprocessors such as first processor 130 and second processor 135 that areconfigured to execute executable code on the HES 100. As discussedabove, in various embodiments, first processor 130 and second processor135 may be configured to execute instructions based on different ISAs.Thus, in some embodiments, the first and second processors 130 and 135may not be configured to execute code written for the other processor.In some embodiments, the processors may comprise a CPU and a GPU; inother embodiments, different processors be utilized. In variousembodiments, more than two processors may be utilized as well.

In various embodiments, the first and second processors 130 and 135 maybe configured to utilize virtual memory. In particular, in variousembodiments, the first and second processors 130 and 135 may beassociated with multiple page tables, such as page tables 140 and 150,in order for a virtual memory manager to translate virtual memoryaddresses to be accessed by the processors to physical memory addresses.In various embodiments, the multiple page tables 140 and 150 may beconfigured to translate one or more virtual memory addresses intodistinct physical memory addresses that are associated withcode-containing memory regions. Thus, as illustrated in FIG. 1, the pagetables 140 and 150 may each contain information that executable code isto be nominally found at a specific set of virtual memory addresses(e.g., the set of virtual memory addresses illustrated as EC VMaddresses 155). However, in various embodiments, the page tables 140 and150 may each be configured to translate these virtual memory addressesto separate physical memory addresses of physical memory locations wherethe executable code are actually found. Thus, as illustrated in FIG. 1,the page tables 140 and 150 may be configured to translate the addressesout of the set of addresses of EC VM addresses 155 to either the sets ofphysical memory addresses EC 1 physical addresses 170 or EC 2 physicaladdresses 180, depending on the page table used for translation. Asdiscussed above, the use of these multiple page tables by the HES 100allows multiple versions of executable code to be selectively used bythe HES 100, while still allowing for a single virtual memory address tobe used to point to the code, as if there were only one version.

FIG. 2 illustrates an example virtual machine monitor 200 (“VMM 220”) ofthe HES 100, in accordance with various embodiments. In variousembodiments, the VMM 200 may be configured to implement one or moreoperations of the HES 100 described herein. In various embodiments, theVMM 200 may be configured to translate memory accesses by the firstand/or second processors 130 and 135. For example, the first processor130 and/or second processor 135 may execute guest software in a virtualmachine (not illustrated) that utilizes virtual memory. As part ofoperation of the guest software, the first processor 130 and/or thesecond processor 135 may seek to perform memory accesses at one or morevirtual memory addresses. In some embodiments, these memory accesses maycomprise code fetches and/or data accesses.

As illustrated in FIG. 2, the VMM 200 may include the page tables 140and 150. In various embodiments, the page tables 140 and/or 150 may beconfigured to be associated with the first and second processors 130 and135. In some embodiments, either of the page tables 140 and 150 may beassociated with only a single processor; in other embodiments, either orboth of the page tables 140 and 150 may be associated with multipleprocessors. In embodiments, if a page table is associated with multipleprocessors, those processors may be configured to operate according tothe same ISA.

In embodiments, the page tables 140 and 150 may be configured to show acommon set of virtual memory addresses as addressing the same executablecode. Embodiments, of this common set of virtual memory addresses isdemonstrated in Figure by the set of EC VM addresses 155 that iscontained in the same location in each of page tables 140 and 150. Invarious embodiments, addresses in the EC VM addresses 155 may be mappedby each of the page tables 140 and 150 into separate sets of physicalmemory addresses, such as EC 1 physical addresses 170 and EC 2 physicaladdresses 180. As discussed above, in various embodiments, these sets ofphysical memory addresses may be determined by a loader 120 that isconfigured to store various versions of executable code into physicalmemory at different locations encompassed by EC 1 physical addresses 170and EC 2 physical addresses 180.

As discussed above, in various embodiments, while the page tables 140and 150 may be configured to map a set of common virtual memoryaddresses for executable code to separate physical memory addresses.Additionally, in various embodiments, the page tables 140 and 150 may beconfigured to map virtual memory addresses associated with data storageto a common set of physical memory addresses. Thus, as illustrated, thepage tables 140 and 150 may be configured to map virtual memoryaddresses from a set of data virtual memory addresses 210 to a set ofdata physical memory addresses 220. In various embodiments, thesedata-associated virtual memory addresses may be associated with the sameset of physical memory addresses by every one of the multiple pagetables utilized by the HES 100. In embodiments, by utilizing page tables140 and 150 that map data-associated virtual memory addresses to thesame physical memory addresses, the VMM 200 of the HES 100 may allow theheterogenous first processor 130 and second processor 135 to have accessto the same data while still facilitating the usage of functionpointers, such as described above.

FIG. 3 illustrates an example HES 100 process 300, in accordance withvarious embodiments. In various embodiments, process 300 may beperformed to compile, load, and execute executable code on the HES 100.The process may begin at operation 310, where the compiler 110 maycompile a portion of source code 105 into multiple versions ofexecutable code, such as versions of executable code 113 and 115. Asdiscussed above, in various embodiments, each of the versions ofexecutable code may contain instructions that are based on a differentISA, and thus may each be executable by a different processor in the HES100. Next, at operation 320, the loader 120 may load the differentversions of the executable code into the HES 100. Particular embodimentsof this operation are discussed below with reference to process 400 ofFIG. 4. Next, at operation 330, the HES 100 may selectively executeappropriate versions of the executable code using multiple page tables.In embodiments, operation 330 may include one or more code fetches usingfunction pointers. Particular embodiments of these code fetches arediscussed below with reference to process 500 of FIG. 5. The process maythen end.

FIG. 4 illustrates an example HES 100 process 400, in accordance withvarious embodiments. The process may begin at operation 420, where theloader 120 may determine sizes of the different versions of theexecutable code that were generated by the compiler 110. Then, atoperation 430, the loader 120 may select virtual memory addresses to bemapped to the different versions of the executable code based on thesizes determined at operation 420. In various embodiments, the loadermay be configured to select the largest size of the different versionsof executable code as a size for the set of virtual memory addressesthat will be mapped to the versions of the executable code. Inembodiments, by selecting the largest size, the loader 120 may beconfigured such that the set of virtual memory addresses is at least aslarge as any one version of executable code stored in physical memory.Additionally, by selecting the largest size, the loader 120 may betterprovide for functions to be found consistently at the same virtualmemory addresses by any processor, regardless of the size of a versionof executable code used by that processor. In embodiments, the set ofvirtual memory addresses may therefore be padded, such as when comparedto a smaller-sized version of executable code, to reach this selected.

Next, at operation 440, the loader 120 may be configured to toadmultiple versions of executable code into physical memory. In variousembodiments, the loader may load each version of executable code intomemory at contiguous sets of physical memory addresses; in otherembodiments, each version of executable code may be stored in separatediscontiguous physical memory segments. In various embodiments, theloader 120 may be configured to load the various versions of executablecode into equal-sized segments of the physical memory. In variousembodiments, the loader 120 may be configured to load the variousversions of executable code into segments of the physical memory equalin size to the size selected at operation 430. Thus, in someembodiments, the loader 120 may be configured to pad the physical memorytaken up by a smaller version of executable code so that that version ofexecutable code takes up the same amount of physical memory space asother versions. In other embodiments, the multiple versions ofexecutable code may be stored in different-sized segments of memory,regarless of whether they are mapped-to by the same set of virtualmemory addresses.

Next, at operation 450, the loader 120 may be configured to configurethe page tables, such as page tables 140 and 150 to include the virtualmemory addresses for the various versions of the executable code. Invarious embodiments, the loader may generate the page tables atoperation 450. In other embodiments, the loader 120 may be configured towrite the mapping between the virtual memory addresses and the physicalmemory addresses for the various versions of the executable code intoalready-created page tables. In yet other embodiments, the loader 120may be configured to provide information on the mapping to the VMM 100(or other entity) for creation or configuration of the page tables 140and 150. The process may then end.

FIG. 5 illustrates an example HES 100 code fetch process 500, inaccordance with various embodiments. In various embodiments, process 500may he performed through execution of a process on a processor where afunction pointer is passed to the process and the processor attempts toswitch execution to a function pointed to by the function pointer. Whileprocess 500 is described with reference to a single processor, it may berecognized that, in various embodiments, the process may be repeated fora different processor in the HES 100 using the same function pointer.

The process may begin at operation 510, where the process executing onone of the processors of the HES 100 may receive the function pointer.In various embodiments, the function pointed to may he associated withthe source code 105 and one of the versions of executable code 113 or115 described above.

Next, at operation 520, the HES 100 may determine a virtual memoryaddress from the function pointer that points to the executable code forthe function. As discussed above, in various embodiments, the virtualmemory address may be the same regardless of which processor the currentprocess is executing on. Next, at operation 530, the processor mayattempt a code fetch for the executable code pointed to by the functionpointer (e.g., the executable code the processor expects to find at thevirtual memory address determined at operation 520).

Next at operation 540, the VMM 200 may translate the virtual memoryaddress using the page table associated with the processor (e.g. pagetable 140 or 150). Then, at operation 550, the processor may accessexecutable code from physical memory that is found at the translatedphysical memory address, accessed code may then be executed by theprocessor at operation 560. The process may then end.

FIG. 6 illustrates, for one embodiment, an example computer system 600suitable for practicing embodiments of the present disclosure. Asillustrated, example computer system 600 may include control logic 608coupled to at least one of the processor(s) 604, system memory 612coupled to system control logic 608, non-volatile memory (NVM)/storage616 coupled to system control logic 608, and one or more communicationsinterface(s) 620 coupled to system control logic 608. In variousembodiments, the one or more processors 604 may be a processor core.

System control logic 608 for one embodiment may include any suitableinterface controllers to provide for any suitable interface to at leastone of the processor(s) 604 and/or to any suitable device or componentin communication with system control logic 608.

System control logic 608 for one embodiment may include one or morememory controller(s) to provide an interface to system memory 612.System memory 612 may be used to load and store data and/orinstructions, for example, for system 600. In one embodiment, systemmemory 612 may include any suitable volatile memory, such as suitabledynamic random access memory (“DRAM”), for example.

System control logic 608, in one embodiment, may include one or moreinput/output (“I/O”) controller(s) to provide an interface toNVM/storage 816 and communications interface(s) 620.

NVM/storage 616 may be used to store data and/or instructions, forexample. NVM/storage 616 may include any suitable non-volatile memory,such as flash memory, for example, and/or may include any suitablenon-volatile storage device(s), such as one or more hard disk drive(s)(“HDD(s)”), one or more solid-state drive(s), one or more compact disc(“CD”) drive(s), and/or one or more digital versatile disc (“DVD”)drive(s), for example.

The NVM/storage 616 may include a storage resource physically part of adevice on which the system 600 is installed or it may be accessible by,hut not necessarily a part of, the device. For example, the NVM/storage616 may be accessed over a network via the communications interface(s)620.

System memory 612 and NVM/storage 616 may include, in particular,temporal and persistent copies of heterogenous execution logic 624. Theheterogenous execution logic 624 may include instructions that whenexecuted by at least one of the processor(s) 604 result in the system600 practicing one or more of the heterogenous execution with multiplepage table-related operations described above. In some embodiments, theheterogenous execution logic 624 may additionally/alternatively belocated in the system control logic 608.

Communications interface(s) 620 may provide an interface for system 600to communicate over one or more network(s) and/or with any othersuitable device. Communications interface(s) 620 may include anysuitable hardware and/or firmware, such as a network adapter, one ormore antennas, a wireless interface, and so forth. In variousembodiments, communication interface(s) 620 may include an interface forsystem 600 to use NFC, optical communications (e.g., barcodes),BlueTooth or other similar technologies to communicate directly (e.g.,without an intermediary) with another device.

For one embodiment, at least one of the processor(s) 604 may be packagedtogether with system control logic 608 and/or heterogenous executionlogic 624. For one embodiment, a least one of the processor(s) 604 maybe packaged together with system control logic 608 and/or heterogenouslogic 624 to form a System in Package (“SiP”). For one embodiment, atleast one of the processor(s) 804 may be integrated on the same die withsystem control logic 608 and/or heterogenous execution logic 624. Forone embodiment, at least one of the processor(s) 604 may be integratedon the same die with system control logic 608 and/or heterogenousexecution logic 624 to form a System on Chip (“SoC”).

The following paragraphs describe examples of various embodiments. Invarious embodiments, a heterogenous computing apparatus for executing afunction on the heterogenous computing apparatus may include a physicalmemory. The apparatus may also include a first computer processorcoupled to the physical memory and configured to support a firstinstruction set architecture. The apparatus may also include a secondcomputer processor coupled to the physical memory and configured tosupport a second instruction set architecture. The apparatus may alsoinclude a virtual machine manager configured to operate on one or morecomputer processors of the apparatus to translate virtual memoryaddresses to physical memory addresses. The virtual memory manager maybe configured to operate to translate a virtual memory addressassociated with a code fetch by the first or the second computerprocessor into a corresponding physical memory address of the physicalmemory, using a selected one of a first page table or a second pagetable, wherein which of the first or the second page table is useddepends on whether the virtual memory address is associated with thecode fetch by the first or the second computer processor.

In various embodiments, the first page table may be configured to mapthe virtual memory address to a first physical memory address, and thesecond page table may be configured to map the virtual memory address toa second physical memory address that is different from the firstphysical memory address. In various embodiments, the physical memory maybe configured to contain first executable code for the function in afirst physical memory region that includes the first physical memoryaddress and second executable code for the function in a second physicalmemory region that includes the second physical memory address, and thefirst and second physical memory regions may be different physicalmemory regions. In various embodiments, the first and second instructionset architectures may be distinct. In various embodiments, the firstexecutable code may include instructions of the first instruction setarchitecture and the second executable code may include instructions ofthe second instruction set architecture.

In various embodiments, the apparatus may further include a loaderconfigured to operate on one or more computer processors of theapparatus. The loader may be configured to load the first executablecode into the first physical memory region and to load the secondexecutable code into the second physical memory region. In variousembodiments, the loader may be further configured to operate tofacilitate configuration the first and second page tables to map thevirtual memory address associated with the code fetch to thecorresponding first and second physical memory addresses.

In various embodiments, the virtual memory address may be associatedwith the code fetch based on a function pointer comprising the virtualmemory address, the function pointer being available to both the firstcomputer processor and the second computer processor. In variousembodiments, the virtual memory address may be passed as an argument toboth executable code executing on the first computer processor andexecutable code executing on the second computer processor.

In various embodiments, a computer-implemented method may facilitateexecution of code on a heterogenous computing device comprising a firstcomputer processor utilizing a first instruction set and a secondcomputer processor utilizing a second instruction set. The method mayinclude loading, by a loader operating on the computing device, firstexecutable code for the function based on the first instruction set andsecond executable code for the function based on the second instructionset into physical memory of the computing device at respective first andsecond physical memory regions, the loading performed in response to arequest to load executable code for a function into memory on thecomputing device, the executable code comprising first executable codeand second executable code for the function based on the secondinstruction set. The method may also include facilitating, by theloader, configuration of first and second page tables for use intranslating virtual memory accesses made by the corresponding first andsecond computer processors, the first and second page tables mapping avirtual memory address for a code fetch to the function to physicaladdresses in the corresponding first and second physical memory regions.

In various embodiments, the method may further include facilitatingconfiguration, by the loader, of the first and second page tables to mapvirtual memory addresses associated with a common virtual memory regionincluding the virtual memory address for the code fetch to physicalmemory addresses of the first and second physical memory regions.

In various embodiments, the method may further include selecting, by theloader, a size for the common virtual memory region based on respectivesizes of the first executable code and the second executable code. Invarious embodiments, selecting the size may include selecting the commonsize based at least in part on a larger of a size of the firstexecutable code and a size of the second executable code.

Computer-readable media (including non-transitory computer-readablemedia), methods, systems and devices for performing the above-describedtechniques are illustrative examples of embodiments disclosed herein.Additionally, other devices in the above-described interactions may beconfigured to perform various disclosed techniques.

Although certain embodiments have been illustrated and described hereinfor purposes of description, a wide variety of alternate and/orequivalent embodiments or implementations calculated to achieve the samepurposes may be substituted for the embodiments shown and describedwithout departing from the scope of the present disclosure. Thisapplication is intended to cover any adaptations or variations of theembodiments discussed herein. Therefore, it is manifestly intended thatembodiments described herein be limited only by the claims.

Where the disclosure recites “a” or “a first” element or the equivalentthereof, such disclosure includes one or more such elements, neitherrequiring nor excluding two or more such elements. Further, ordinalindicators (e.g., first, second or third) for identified elements areused to distinguish between the elements, and do not indicate or imply arequired or limited number of such elements, nor do they indicate aparticular position or order of such elements unless otherwisespecifically stated.

What is claimed is:
 1. One or more non-transitory computer-readable storage media having instructions embodied therein that are configured, in response to execution by a computing device comprising a first computer processor and a second computer processor, to cause the computing device to operate a virtual machine manager to translate virtual memory addresses to physical memory addresses, wherein the virtual memory manager is configured to translate a virtual memory address associated with a code fetch by the first or the second processor into a corresponding physical memory address of a physical memory location, using a selected one of a first page table or a second page table correspondingly associated with the first and second processors, wherein which of the first and second page tables is used depends on whether the code fetch is associated with the first or the second processor.
 2. The one or more computer-readable storage media of claim 1, wherein: the first page table maps the virtual memory address associated with the code fetch to a first physical memory address, and the second page table maps the virtual memory address associated with the code fetch to a second physical memory address that is different from the first physical memory address.
 3. The one or more computer-readable storage media of claim 2, wherein the first physical memory address is associated with a first physical memory region having first executable code of a first instruction set architecture of the first processor, and the second physical memory address is associated with a second physical memory region having second executable code of a second instruction set architecture of the second processor, wherein the first and second physical memory regions are different physical memory regions, and the first and second instruction set architectures are different instruction set architectures.
 4. The one or more computer-readable storage media of claim 3, wherein the first and second page tables are configured to map virtual memory addresses associated with a common virtual memory data region to physical memory addresses of a common physical memory region.
 5. The one or more computer-readable storage media of claim 3, wherein the first executable code and the second executable code are each generated from common source code.
 6. The one or more computer-readable storage media of claim 5, wherein the instructions are further configured, in response to execution by the computing device, to cause the computing device to operate a loader to load the first executable code and the second executable code into the corresponding first and second physical memory regions.
 7. The one or more computer-readable storage media of claim 6, wherein the loader is configured to facilitate configuration of the first and second page tables to map the virtual memory address associated with the code fetch to the corresponding first and second physical memory addresses.
 8. The one or more computer-readable storage media of claim 7, wherein the loader is configured to facilitate configuration of the first and second page tables to map virtual memory addresses associated with a common virtual memory region including the virtual memory address associated with the code fetch to physical memory addresses of the first and second physical memory regions.
 9. The one or more computer-readable storage media of claim 8, the loader is configured to select a size for the common virtual memory region based at least in part on the respective sizes of the first executable code and the second executable code.
 10. The one or more computer-readable storage media of claim 9, wherein the loader is configured to select the size for the common virtual memory region based at least in part on a larger of a size of the first executable code and a size of the second executable code.
 11. The one or more computer-readable storage media of claim 1, wherein the virtual memory address is associated with the code fetch based on a function pointer comprising the virtual memory address, the function pointer being available to both the first computer processor and the second computer processor.
 12. The one or more computer-readable storage media of claim 11, wherein the virtual memory address is to be passed as an argument to both executable code executing on the first computer processor and executable code executing on the second computer processor.
 13. One or more non-transitory computer-readable storage media having instructions embodied therein that are configured, in response to execution by a computing device comprising a first computer processor utilizing a first instruction set and a second computer processor utilizing a second instruction set, to cause the computing device to operate a loader to: respond to a request to load executable code for a function into memory on the computing device, wherein the executable code comprises first executable code for the function based on the first instruction set and second executable code for the function based on the second instruction set, wherein response to the request includes performance of a load of the first executable code and the second executable code into physical memory of the computing device at respective first and second physical memory regions; facilitate configuration of first and second page tables for use in translating virtual memory accesses made by the corresponding first and second computer processors, wherein the first and second page tables are to map a virtual memory address for a code fetch of the function to physical memory addresses in the corresponding first and second physical memory regions.
 14. The one or more computer-readable storage media of claim 13, wherein the loader is configured to facilitate configuration of the first and second page tables through facilitation of configuration of the first and second page tables to map virtual memory addresses associated with a common virtual memory region including the virtual memory address for the code fetch to physical memory addresses of the first and second physical memory regions.
 15. The one or more computer-readable storage media of claim 14, wherein the loader is configured to select a size for the common virtual memory region based on respective sizes of the first executable code and the second executable code.
 16. The one or more computer-readable storage media of claim 15, wherein the loader is configured to select the size based at least in part on a larger of a size of the first executable code and a size of the second executable code.
 17. A heterogenous computing apparatus for executing a function on the heterogenous computing apparatus comprising: a physical memory; a first computer processor coupled to the physical memory and configured to support a first instruction set architecture; a second computer processor coupled to the physical memory and configured to support a second instruction set architecture; and a virtual machine manager configured to operate on one or more computer processors of the apparatus to translate virtual memory addresses to physical memory addresses; wherein the virtual memory manager is configured to operate to translate a virtual memory address associated with a code fetch by the first or the second computer processor into a corresponding physical memory address of the physical memory, using a selected one of a first page table or a second page table, wherein which of the first or the second page table is used depends on whether the virtual memory address is associated with the code fetch by the first or the second computer processor.
 18. The apparatus of claim 17, wherein: the first page table is configured to map the virtual memory address to a first physical memory address, and the second page table is configured to map the virtual memory address to a second physical memory address that is different from the first physical memory address.
 19. The apparatus of claim 18, wherein: the physical memory is configured to contain first executable code for the function in a first physical memory region that includes the first physical memory address and second executable code for the function in a second physical memory region that includes the second physical memory address; and the first and second physical memory regions are different physical memory regions.
 20. The apparatus of claim 19, wherein the first and second instruction set architectures are distinct.
 21. (canceled)
 22. The apparatus of claims 18, further comprising a loader configured to operate on one or more computer processors of the apparatus to: load the first executable code into the first physical memory region; and load the second executable code into the second physical memory region.
 23. The apparatus of claim 22, wherein the loader is further configured to operate to facilitate configuration of the first and second page tables to map the virtual memory address associated with the code fetch to the corresponding first and second physical memory addresses.
 24. The apparatus of any of claim 17, wherein the virtual memory address is associated with the code fetch based on a function pointer comprising the virtual memory address, the function pointer being available to both the first computer processor and the second computer processor.
 25. (canceled)
 26. A computer-implemented method for facilitating execution of code on a heterogenous computing device comprising first and second computer processors, the method comprising: translating, by a virtual machine manager operating on a computing device, a virtual memory address associated with a code fetch by the first or the second processor into a corresponding physical memory address of a physical memory location, using a selected one of a first page table or a second page table correspondingly associated with the first and second processors, wherein which of the first or second page table is used depends on whether the virtual memory address is associated with the code fetch by the first or the second processor.
 27. The method of claim 26, wherein: the first page table maps the virtual memory address to a first physical memory address, and the second page table maps the virtual memory address to a second physical memory address that is different from the first physical memory address.
 28. (canceled)
 29. (canceled)
 30. (canceled)
 31. (canceled)
 32. (canceled)
 33. (canceled)
 34. (canceled)
 35. (canceled)
 36. (canceled)
 37. (canceled)
 38. (canceled)
 39. A computer-implemented method for facilitating execution of code on a heterogenous computing device comprising a first computer processor utilizing a first instruction set and a second computer processor utilizing a second instruction set, the method comprising: loading, by a loader operating on the computing device, first executable code for the function based on the first instruction set and second executable code for the function based on the second instruction set into physical memory of the computing device at respective first and second physical memory regions, the loading performed in response to a request to load executable code for a function into memory on the computing device, the executable code comprising first executable code and second executable code for the function based on the second instruction set; facilitating, by the loader, configuration of first and second page tables for use in translating virtual memory accesses made by the corresponding first and second computer processors, the first and second page tables mapping a virtual memory address for a code fetch to the function to physical addresses in the corresponding first and second physical memory regions.
 40. The method of claim 39, further comprising facilitating configuration, by the loader, of the first and second page tables to map virtual memory addresses associated with a common virtual memory region including the virtual memory address for the code fetch to physical memory addresses of the first and second physical memory regions.
 41. (canceled)
 42. (canceled) 